『A Philosophy of Software Design』

https://m.media-amazon.com/images/P/173210221X.01._SCLZZZZZZZ_SX500_.jpg

初版 2018

第2版 2021

it is important for a module to have a simple interface than a simple implementation.（p.61）

目次

1 Introduction

2 The Nature of Complexity

3 Working Code Isn't Enough

4 Modules Should Be Deep

5 Information Hiding (and Leakage)

6 General-Purpose Modules are Deeper

7 Different Layer, Different Abstraction

8 Pull Complexity Downwards

9 Better Together Or Better Apart?

10 Define Errors Out Of Existence

11 Design it Twice

12 Why Write Comments? The Four Excuses

13 Comments Should Describe Things that Aren't Obvious from the Code

14 Choosing Names

15 Write The Comments First

16 Modifying Existing Code

17 Consistency

18 Code Should be Obvious

19 Software Trends

20 Designing for Performance

21 Decide What Matters

22 Conclusion

日本語の関連記事